-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the cleanupexamples tool #215
Conversation
Signed-off-by: Fatih Türken <[email protected]>
0723e84
to
cad2a3c
Compare
Signed-off-by: Fatih Türken <[email protected]>
cad2a3c
to
fd90fee
Compare
Signed-off-by: Fatih Türken <[email protected]>
Signed-off-by: Fatih Türken <[email protected]>
0d9c01e
to
6fd8e14
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @turkenf, especially for providing unit tests as well 😎 Please find my comments below. I'm approving the PR, in case you would like to merge soon. I would be happy to see another review though, just to have another point of view.
Signed-off-by: Fatih Türken <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @turkenf for your great work here. LGTM!
Description of your changes
We publish some uptest specific codes in the example manifests to the Upbound marketplace. For example, we add the annotation
upjet.upbound.io/manual-intervention
to skip uptest in resources that require manual intervention, or we add${Rand.RFC1123Subdomain}
to generate a random value in fields that require a unique string.These uptest specific codes and placeholders can be confusing for users. See as an example: crossplane-contrib/provider-upjet-aws#988
This PR adds the
cleanupexamples
tool, which removes the above-mentioned confusion.I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
For now, this tool has been tested manually in my local environment. We will do more testing when we integrate the code into the build process.